Network Supervisor's Toolkit

home *** CD-ROM | disk | FTP | other *** search

/ Network Supervisor's Toolkit / Network Supervisor's Toolkit.iso / patches / _311ptch / 311pt7 / 311pt7.doc next >

Wrap

Text File | 1996-07-10 | 38.5 KB | 908 lines

README FILE FOR 311PT7.ZIP ********** Warning ******************************************************* Load ONLY the specific NLM that corrects the problem you are experiencing. ************************************************************************** This file contains the latest release of NetWare v3.11 Operating System Patches. The following files are included in this release: 311PT7 DOC (This file) AFPFIX1 NLM 2663 1-06-92 7:22p ASNCRDFX NLM 1508 4-20-92 1:51p BIGRFIX NLM 1425 4-22-92 3:36p CLPHFIX NLM 1238 6-16-92 7:59a CROPNFX NLM 1040 12-18-91 3:18p DIAGRFSX NLM 2593 3-18-92 8:21a DIRLPFIX NLM 1508 12-12-91 1:07p DOSUNFIX NLM 1910 4-22-92 10:35a DOTFIX NLM 1343 12-12-91 1:29p EAINFIX NLM 1600 3-09-92 10:59a EVENTFIX NLM 2174 12-12-91 1:47p FATFIX NLM 3357 4-23-92 12:53p GETQFIX NLM 1211 3-23-92 2:57p GETRFIX NLM 1311 4-22-92 3:38p GETSEFIX NLM 1463 4-22-92 10:41a GNSFIX NLM 2397 2-19-92 1:43p HTFXFX NLM 1036 3-24-92 1:25p MAXCDCFX NLM 942 12-18-91 3:19p MFIXOPEN NLM 1459 10-03-91 5:00p MKDIRFIX NLM 2071 12-12-91 1:49p NCPSPFIX NLM 1644 10-04-91 9:13a OS2OPNFX NLM 1389 11-22-91 2:45p PAPFIX1 NLM 1145 12-02-91 3:18p PAPFIX3 NLM 1310 1-08-92 10:32a PATCHMAN NLM 9051 4-16-92 11:21a PCHMN223 DOC 6110 5-07-92 4:33p REMDEVFX NLM 1299 10-03-91 5:04p REQFIX NLM 1235 2-19-92 1:39p SPXFIX1 NLM 1513 3-13-92 12:32p SPXFSFIX NLM 1617 12-12-91 1:59p SYNCTIME NLM 2131 12-17-91 4:17p TRSTFIX NLM 1621 12-17-91 4:52p TTSFIX NLM 1049 1-06-92 3:35p UNKFIX NLM 1050 2-19-92 1:52p WORMROFX NLM 1081 10-03-91 4:49p WSDFIX NLM 1733 10-09-91 3:39p XMCFIX NLM 1232 2-19-92 1:56p This file supersedes previous releases of the 3.11 OS patches distributed on NetWire under the names 311PT1.ZIP, 311PT2.ZIP, 311PT3.ZIP, 311PT4.ZIP, 311PT5.ZIP and 311PT6.ZIP. The following patches were added to create 311PT2.ZIP: GNSFIX NLM 2397 02-19-92 1:43p EAINFIX NLM 1600 03-09-92 10:59a MAXCDCFX NLM 942 12-18-91 3:19p REQFIX NLM 1235 02-19-92 1:39p TTSFIX NLM 1049 01-06-92 3:35p UNKFIX NLM 1050 02-19-92 1:52p The following patches were added to create 311PT3.ZIP: CROPNFX NLM 1040 12-18-91 3:18p DIAGRFSX NLM 2593 03-18-92 8:21a GETQFIX NLM 1211 03-23-92 2:57p HTFXFX NLM 1036 03-24-92 1:25p PATCHMAN NLM 8987 03-12-92 11:24a PCHMN222 DOC 6110 04-03-92 10:49a SPXFIX1 NLM 1513 03-13-92 12:32p XMCFIX NLM 1232 02-19-92 1:56p The following patches were added to create 311PT4.ZIP: BIGRFIX NLM 1425 4-22-92 3:36p DOSUNFIX NLM 1910 4-22-92 10:35a GETSEFIX NLM 1463 4-22-92 10:41a PATCHMAN NLM 9051 4-16-92 11:21a PCHMN223 DOC 6110 5-07-92 4:33p The following patches were added to create 311PT5.ZIP: FATFIX NLM 3357 4-23-92 12:53p The following changes were made to create 311PT6.ZIP: GETRFIX NLM 1311 4-22-92 3:38p (Added) ELRDFIX NLM 2953 12-17-91 4:33p (Deleted) ***************************************************************** ELRDFIX.NLM was removed because of possible data corruption with this patch loaded in conjunction with running Vrepair. ***************************************************************** The following patches were added to create 311PT7.ZIP: CLPHFIX NLM 1238 6-16-92 7:59a ASNCRDFX NLM 1508 4-20-92 1:51a IMPORTANT NOTES: 1. Patches for the 3.11 Operating System included with this release are for all number-of-user versions of NetWare v3.11. (With the exception of the single user, or run time version) There are some specific notes regarding the use of these patches with any 3.11 Operating System patches dated prior to October of 1991. These notes are included below under the heading NOVELL TECHNICAL BULLETIN and should be reviewed by anyone using these patches. 2. A second documentation file by the name of PCHMN223.DOC is included, which accompanies PATCHMAN.NLM. PATCHMAN.NLM is required when loading these patches. 3. Each of the patches included in this release is listed below along with a description and a list of files it replaces. 4. Also included below is a brief discussion of the patch concept and installation instructions. 5. Note that specific instructions are given for the use of FATFIX.NLM below the description of that patch. DESCRIPTION OF THE PATCHES AFPFIX1 NLM 2663 01-06-92 7:22p This patch is only for NetWare for Macintosh. AFPFIX1.NLM corrects a problem with copying folders (containing files) into drop boxes on a NetWare v3.11 server. This patch fixes all known drop box problems in both System 6 and 7 for all released versions of AFP.NLM. This patch supersedes the original AFPFIX1.NLM version and the correction in AFP.NLM v3.01. **NOTE: This patch supersedes AFPFIX.NLM (4-11-91 907) previously distributed under the name AFPFIX.ZIP on forum NOVLIB, library 8 ASNCRDFX NLM 1508 04-20-92 1:51p This patch fixes a problem that may occur when multiple threads do asyncrhonous reads. It is possible for a thread to read data that was written by another thread. This problem has been known to occur with the Btrieve.nlm application if a Btrieve data file page size is not 512, 1024, 2048 or 4096 bytes. If the page size is not one of these sizes, the data file may become corrupt. BIGRFIX NLM 1425 4-22-92 3:36p This patch allows the OS to prevent "read" requests larger than 512K from overrunning the stack. This problem has been known to occur when loading large NLMs. CLPHFIX NLM 1238 6-16-92 7:59a This patch fixes the "ClearPhantom called with not primary directory number" Abend. CROPNFX NLM 1040 12-18-91 3:18p This patch fixes a problem found when a client makes a request to create or open a file. When a user makes a CreateOpenFile request, the server creates the file, but the server's reply to the user gets lost. The client then makes a second request to create the file, but since it has already been created, the user gets the error message: "file already created." Additionally, when a client request is made to open a file, the server opens the file, but its response to the client is lost. The client makes a second request to open the file, and the server opens the file a second time. This scenario can result in the server keeping the file open while the user thinks it has been closed. This problem becomes apparent when the user attempts to delete the file and receives the error message: "File in use." DIAGRFSX NLM 2593 03-18-92 8:21a This patch fixes two network management errors. The first error caused the server to not respond to requests issued by the network management console (only rebooting would fix the problem). The second error did not allow the File Server to respond to network management requests directed to other networks connected to the File Server other than the Internal Network. DIRLPFIX NLM 1508 12-12-91 1:07p This patch fixes a problem in NetWare 386 v3.11 that results in an infinite loop when the DOS DIR command is used in a subdirectory where more than 65,535 files exist. This loop will also occur with the FindFirst and FindNext DOS function calls. **NOTE: This patch supersedes DIRLPFIX1.NLM (4-9-91 797) previously distributed under the name DRLFX1.ZIP. It also supersedes DIRLPFIX.NLM (10-2-91 1532) previously distributed under the name of DRLFX1.ZIP in the NSD area of Netwire. DOSUNFIX NLM 1910 4-22-92 10:35a This patch fixes a problem with NetWare/NFS V1.2. If a file is renamed from 99999999.v0 to 99999999.V0, it causes the server to ABEND with the message: "DOSGenerateUniqueName tried over 100000000 names and couldn't get a unique one." **NOTE: This patch supersedes DOSUNFIX.NLM (3-19-92 1662) previously distributed under the name of DOSUN.ZIP in the NSD area of Netwire. DOTFIX NLM 1343 12-12-91 1:29p This patch fixes the problem of multiple directories of the same name being created at the SYS: (root) level. Currently, if the user creates directories ending in two dots: ".." (e.g. "STATS.."), multiple directories of the same name will be created. A directory listing using DIR will show multiple directories of the same name. For example: >DIR STATS <DIR> STATS <DIR> STATS <DIR> DOTFIX.NLM fixes the problem so that if the user tries to create directories with the same name, the error message "Unable to create directory" appears. **NOTE: This file supersedes DOTFIX.NLM (10-2-91 1351) previously distributed under the name of DOTFIX.ZIP in the NSD area of Netwire. EAINFIX NLM 1600 03-09-92 10:59a This patch fixes a problem with Extended Attributes when two or more work stations execute XCOPY multiple times. The result is that after about ten minutes the server will ABEND with the message: "Free called with a memory block that has an invalid resource tag.". **NOTE: This file (EAINFIX.NLM) was previously distributed under the name EAINFIX.ZIP direct from Novell on a Field Test (or BETA) basis. This file has passed testing. EVENTFIX NLM 2174 12-12-91 1:47p This patch is required by any NLM that needs object deletion notification. Symptoms of this bug will vary, depending on the NLM being run. It addresses a problem that occurs when a "delete bindery object" call is made to the OS. The OS reports the event after the object is already deleted, thus preventing the application from accessing information on the object when the event is reported. This patch fixes this problem; the bindery object is not deleted until after the event is reported. **NOTE: This file supersedes EVENTFIX.NLM(10-2-91 2206) previously distributed under the name OBJDEL.ZIP in the NSD area of Netwire. FATFIX NLM 3357 4-23-92 12:53p This patch fixes a problem with TurboFAT and FAT corruption in general, when multiple workstations randomly access large database files. ********* IMPORTANT SPECIFIC INSTRUCTIONS FOR FATFIX.NLM ********* It is important to note that the latest version of VREPAIR.NLM should be run before implementing this patch. FATFIX.NLM will prevent corruption of the FAT and TURBOFAT, but VREPAIR is required to correct previous corruption. The steps below should guide you through using FATFIX.NLM. 3. In order to use this patch, first add the following two lines to your AUTOEXEC.NCF file after the assignment of the "IPX INTERNAL NET" number (See page 150 of the NetWare v3.11 "Installation" manual for an example of this statement): LOAD PATCHMAN LOAD FATFIX It is important that these lines are added immediately after the assignment of the internal network number. After editing, be sure to save the file. 2. After editing the AUTOEXEC.NCF file do the following things: 2a. LOAD VREPAIR at the console. 2b. Dismount the volumes. 2c. Run VREPAIR on all volumes until there are no further errors reported (This make take one or more attempts). 2d. Down the server. 2e. Bring the server back up with the modified AUTOEXEC.NCF file. **NOTE: This file (FATFIX.NLM) was previously distributed under the name FATFIX.ZIP direct from Novell on a Field Test (or BETA) basis. This file has passed testing. GETQFIX NLM 1211 03-23-92 2:57p This patch fixes a problem which caused a large number of deleted .SRV files in the queue subdirectories in SYS:SYSTEM. **NOTE: This file supersedes GETQFIX.NLM (1211 03-11-92 11:56a) previously distributed under the name GETFIX.ZIP direct from Novell on a Field Test (or BETA) basis. This file has passed testing. GETRFIX NLM 1311 04-22-92 3:38p This patch fixes an abend caused by a driver requesting a valid linked request, which has been changed by another process. A zero is now returned to the calling process instead of abending the server. GETSEFIX NLM 1463 4-22-92 10:41a This patch fixes a problem found when more than 31 security equivalences for a user or group ID are set up. This can result in a system hang which may be accompanied by a message indicating a "multiple abend". **NOTE: This file supersedes GETSEFIX.NLM (3-18-92 1299) previously distributed under the name GETSE.ZIP in the NSD area of Netwire. GNSFIX NLM 2397 02-19-92 1:43p This patch fixes a problem found when rebooting and attempting to get a connection to the file server. If all of the connections are in use, (e.g. 20 for the 20-user version, 50 for the 50-user version, etc.), and one of the users reboots, the user will not be able to log back in to the server. This problem will only occur if there is only one network. If the user is on an internet, a re-connection will be possible. The problem is that once a user reboots, his connection is not terminated at the server until a time out limit is reached (usually 15 minutes). This patch corrects the problem by checking the source node address of the incoming packet to the node address of all workstations the server currently thinks it is attached to. If a match is found the server responds to the workstation, thus re-creating a connection in the same slot the workstation had prior to its reboot. **NOTE: This file supersedes GNSFIX.NLM (12-4-91 2484) previously distributed under the name GNSFIX.ZIP in the NSD area of Netwire. HTFXFX NLM 1036 03-24-92 1:25p Corrects a problem when using disk block sizes larger than 4K and cache buffer sizes larger than 4K. If a block was read from the redirection area while copying a file in the above circumstance, it could cause the destination block to become corrupted. **NOTE: This file is the same file as HTFXFX.NLM (1163 03-13-92 10:44a) previously distributed under the name HTFXFX.ZIP direct from Novell on a Field Test (or BETA) basis. This file has passed testing. MAXCDCFX NLM 942 12-18-91 3:19p This patch changes the maximum limit for the Set Parameter "Maximum Concurrent Disk Cache Writes" from the old range of 10 to 100, to a new range, 10 to 1000. This change will be transparent to most users. The performance of some high throughput disk controller drivers is limited by the slower limit. You may want to load this NLM if your system uses high throughput EISA drives. MFIXOPEN NLM 1459 10-03-91 5:00p This patch is intended for all number-of-user versions of NetWare 386 v3.11 that are running the MAC gateway VAPS instead of the AFP NLMs. This patch fixes the problem that MAC users have when trying to open files that are flagged Read Only. The user is unable to open the file, and receives the error message: "File not found." **NOTE: This file supersedes MFIXOPEN.NLM(7-3-91 1112) previously distributed under the name MFXOP1.ZIP in forum NOVLIB, library 8 of Netwire. It also supersedes MFIXOPEN.NLM (10-2-91 1459) previously distributed under the name MFXOP1.ZIP in the NSD area of Netwire. MKDIRFIX NLM 2071 12-12-91 1:49p This patch corrects invalid error codes returned by the "create directory" call or when copying a file to an invalid path. It replaces and supersedes the previously released patch, DIRHFIX1.NLM. Since DIRHFIX1.NLM and MKDIRFIX.NLM patch some of the same areas, they cannot coexist. To run MKDIRFIX.NLM, DIRHFIX1.NLM must be removed from the system. Additionally, this fix changes error codes returned from "ERR_BAD_DIR_HANDLE-program aborted" to "ERR_INVALID_PATH" in the case where the server is scanning a directory path and a file name exists in the middle of that directory path. (For example: Makedir: dir1/dir2/dir3 where dir2 is a filename.) **NOTE: This file supersedes MKDIRFIX.NLM(10-2-91 2087) previously distributed under the name MKDIR1.ZIP in the NSD area of Netwire. NCPSPFIX NLM 1644 10-04-91 9:13a This patch prevents a zero-length WriteToSpool NCP from being processed. This problem has been known to cause an ABEND:GENERAL PROTECTION PROCESSOR EXCEPTION and corrupt an entire volume. **NOTE: This file supersedes NCPSPFIX.NLM(10-2-91 1644) previously distributed under the name NCPSP1.ZIP in the NSD area of Netwire. OS2OPNFX NLM 1389 11-22-91 2:45p This patch allows a user to use the "TYPE" command to view a file even though SCAN file rights have not been granted. Without this patch, if the user is granted all rights but the SUPERVISOR and SCAN file rights (including Read) the file still cannot be "TYPE"ed. This patch fixes this problem. **NOTE: This file is the same file as OS2OPNFX.NLM previously distributed under the name OS2OPN.ZIP direct from Novell on a Field Test (or BETA) basis. This file has passed testing. PAPFIX1 NLM 1145 12-02-91 3:18p This patch is only for V3.0 NetWare for Macintosh. PAPFIX1.NLM is a patch to APPLETLK.NLM v3.0. This patch resolves a problem where server PAP sessions of greater than 255 transactions would be interrupted and fail. The AppleTalk stack would then generate an error message stating that the Tickle Timer popped on the affected connection. This problem would cause ATPS.NLM to consistently fail to print files over one megabyte in size or to return font lists greater than 255 entries to Macintosh clients. In these circumstances, ATPS would return the message "PAP write: no such device or address". This patch is for use with v3.0 NetWare for Macintosh; the problem is resolved with v3.01 NetWare for Macintosh. **NOTE: This file supersedes PAPFIX1.NLM(4-26-91 1033) previously distributed under the name PAPFIX.ZIP in forum NOVLIB, LIB 8. PAPFIX3 NLM 1310 01-08-92 10:32a This patch is only for V3.0 NetWare for Macintosh. PAPFIX3.NLM modifies APPLETLK.NLM v3.0 to resolve a problem that ATPS.NLM has connecting to certain non-Apple printers that require an incrementing value in the WaitTime field of PAP OpenConn packets. The symptom of this problem visible to users would be that ATPS.NLM generates messages such as "Printer busy, status- idle" and may not advertise the affected queue on AppleTalk. This problem is resolved with v3.01 NetWare for Macintosh. **NOTE: This file supersedes PAPFIX3.NLM(6-5-91 1326) previously distributed under the name PAPFX3.ZIP in forum NOVLIB, LIB 8. PATCHMAN NLM 9051 4-16-92 11:21a PATCHMAN.NLM is the Patch Manager which tracks and manages all dynamic patches for NetWare 386 v3.10 or above. All 3.11 Operating System patches included with this documentation will require PATCHMAN.NLM V2.20 or above. The version of PATCHMAN included in this file is v2.23. Please see PCHMN223.DOC that is included with this file for further explanation on PATCHMAN.NLM. **NOTE: This file supersedes ALL PREVIOUS versions of PATCHMAN (FOR VERSION 3.11 ONLY!) including PCH121.ZIP in forum NOVLIB, LIB 13. REQFIX NLM 1235 02-19-92 1:39p This patch reinitializes the number of requests made from a station each time a new user logs in. This problem was visible when looking at data returned by PAUDIT. If an individual workstation was used to login for several different users, the "requests" value displayed in PAUDIT was not reinitialized for each user. **NOTE: This file (REQFIX.NLM) was previously distributed under the name REQFIX.ZIP direct from Novell on a Field Test (or BETA) basis. This file has passed testing. REMDEVFX NLM 1299 10-03-91 5:04p This patch fixes a problem formatting removable devices. If INSTALL.NLM is loaded and FORMAT is run, the 3.11 Operating System causes an abend with the message "ABEND: Kernel detected a process switch during interrupt time." **NOTE: This file supersedes REMDEVFX.NLM(8-2-91 1107) previously distributed under the name REMDEV.ZIP in forum NOVLIB, LIB 4. It also supersedes REMDEVFX.NLM(10-2-91 1299) previously available under the name REMDEV.ZIP in the NSD area of Netwire. SPXFIX1 NLM 1513 03-13-92 12:32p This patch corrects problems for certain applications that may hang due to lost ECB's. SPXFSFIX NLM 1617 12-12-91 1:59p This patch fixes a problem that results in a file server GPI in the SPXFindSession. This ABEND is known to occur when using Madge "Smart IPX" Token Ring drivers. The problem is caused by a connect request SPX packet which arrives at the server without the system bit being set. This causes the server to look up the session with ID = FFFF (session ID for system packets), but since the system bit isn't set, the server looks in the session table for a client with a corresponding ID. This causes SPXFindSession to look beyond the end of memory, resulting in a GPI ABEND. The patch adds a test to SPXFindSession to check for sessions beyond the end of the session table. With this patch, if a connect request SPX packet is sent without the system bit set, the packet will be discarded as invalid and the workstation that sent the invalid packet will hang. **NOTE: This file supersedes SPXFSFIX.NLM(10-2-91 1625) previously distributed under the name SPXFIX.ZIP in the NSD area of Netwire. SYNCTIME NLM 2131 12-17-91 4:17p This patch forces the server's date/time to be synchronized to the hardware's clock at specified intervals. These NLM's eliminate the gradual loss of time experienced by the server due to "missed" clock ticks while the server is in real mode. **NOTE: This file supersedes SYNC311.NLM(9-27-91 1987) previously distributed under the name TIM386.ZIP in the NSD area of Netwire. **NOTE ALSO: This file should not be confused with TIM386.ZIP located in forum NOVLIB, Library 4, which is for Netware 386 v3.10a and specifically refers to v3.10a in the documentation that comes with that file. TRSTFIX NLM 1621 12-17-91 4:52p This patch fixes a problem found when 9 or more trustee directory assignments for individual users or groups are made at the root level of the same volume (usually volumes other than the SYS: volume). Although the assignments are made as they should be, the 9th and above cannot be seen from SYSCON. (They do appear in FILER or TLIST.) This patch adds a check for the parent of the trustee node that contains the ninth trustee assignment; if the parent node is the root of the volume, it checks for trustee assignments. This patch also fixes a problem found when granting trustee rights to an existing group. The rights appear to be correct in SYSCON when viewed from user SUPERVISOR, but these new rights do not appear when viewed by the individual user. These rights are not actually in effect. When viewed as a group member, the user gets the error: "GetTrusteePaths returned error 242". **NOTE: This file supersedes TRSTFIX.NLM(10-11-91 1603) previously distributed under the name TRSTFX.ZIP in NSD area of Netwire. TTSFIX NLM 1049 01-06-92 3:35p TTSFIX.NLM fixes a bug encountered when certain applications execute explicit TTS, and file locking is also used. This results in an application hang at the workstation, and a GPPE ABEND at the file server. **NOTE: This file is the same file as TTSFIX.NLM previously distributed under the name TTS311.ZIP in NSD area of Netwire. UNKFIX NLM 1050 02-19-92 1:52p This patch fixes a problem which was causes an ABEND on a 3.11 FILE SERVER. This is caused by entering a complete file name of a valid NetWare file at the file server console. This file may be located on any of the server's search paths. FOR EXAMPLE: typing "MONITOR.NLM" at the console instead of "LOAD MONITOR.NLM" will cause the above condition. Typing "MONITOR" without the .NLM extension will not cause the ABEND. If the named file is not an .NCF file the server will repeatedly display: "Unknown command" and "Invalid line in command file-line length exceeds 511 characters" until it eventually would abend with the message: "ABEND: General Protection Processor Exception running console command process." The Operating System is incorrectly attempting to open and read the NLM as if it were an .NCF file. **NOTE: This file supersedes UNKFIX.NLM (1153 1-29-92) previously distributed under the name UNKFIX.ZIP direct from Novell on a Field Test (or BETA) basis. This file has passed testing. WORMROFX NLM 1081 10-03-91 4:49p Currently, if a removable device is initially mounted read/write, and then the cartridge is removed and a new device is inserted that has the write disable tab set, the OS does not recognize that the device is now Read only. This patch fixes this problem. **NOTE: This file supersedes WORMROFX.NLM(8-2-91 929) previously distributed under the name WORMROFX.ZIP in forum NOVLIB, Library 4. It also supersedes WORMROFX.NLM (10-2-91 1081) previously located in the NSD area of Netwire. WSDFIX NLM 1733 10-09-91 3:39p This patch fixes a problem with APIs that allow users to access files on volumes where they have no rights. This patch generates a new handle so that rights are re-enumerated with each volume change. **NOTE: This is the same file as WSDFIX.NLM(10-9-91 1733) previously distributed under the name WSDFIX.ZIP in NSD area of Netwire. XMCFIX NLM 1232 02-19-92 1:56p This patch corrects a problem with utilities that use the SPX protocol to maintain communication with the server. Typically the client will loose the connection to the server and the following message will be displayed: "No more response buffers available" The most common occurrence is with a remote printer(RPRINTER.EXE) loosing it's connection to the print server(PSERVER.NLM), but it may happen with other utilities. This is happens when a call to SPXSendSequencedPacket() resets a session retransmit count which causes it to NOT abort the connection if the connection is broken in one direction and maintained in another. **NOTE: This is the same file as XMCFIX.NLM(1232 02-19-92 1:56p) previously distributed under the name XMCFIX.ZIP in NSD area of Netwire. INSTALLATION AND INFORMATION ABOUT NetWare v3.11 O.S. PATCHES Each of the patches listed above are intended for 386 v.3.11 and are dynamic patches which are loaded at the file server console as a NetWare Loadable Modules. They require PATCHMAN.NLM v2.20 or later in order to load. *** PLEASE NOTE THE TECHNICAL BULLETIN ON THE 3.11 OPERATING SYSTEM PATCHES INCLUDED BELOW. Unlike patches previous to those for Netware 386 v3.10, the SERVER.EXE file is never modified by these patches. These patches patch the Operating System in memory, not on the disk. This means that each patch must be loaded each time before any "fixes" take effect. It is recommended that the command "LOAD <patch name>" be placed in the server's AUTOEXEC.NCF file to ensure that the patch is always in effect when the server is initially brought up. Since they are NLM's, the patches can be loaded and unloaded without ever having to bring the server down. Once loaded, the Operating System is patched and ready to go. Unloading the patches will restore the Operating System to its original "un-patched" state. Like all NLM-type patches, REMDEVFX.NLM requires the Patch Manager (PATCHMAN.NLM) to be loaded before it can be loaded. If PATCHMAN is not already loaded, the first patch will attempt to locate PATCHMAN and load it automatically if found. PATCHMAN only needs to be loaded once. All other patches will load once PATCHMAN is loaded. PATCHMAN cannot be unloaded until all patches that rely on it are first unloaded. Typing "Patches" at the system command line once PATCHMAN is loaded will display all patches currently loaded on the file server. Installation: To install a specific patch or patches, simply place the patch file in the same directory as the other NLM files (SYS:SYSTEM or DOS partition), and type "LOAD <patch name>" for each patch you which to load. Once a patch has loaded, all changes are in effect until it is unloaded. If an error message appears, contact Novell Technical Support. As suggested above, you will probably want to enter the LOAD commands into your AUTOEXEC.NCF file to insure that the patches are loaded automatically. NOVELL TECHNICAL BULLETIN TITLE: Effects of v3.11 Serialization Changes on Patches and Fixes DOCUMENT ID#: TB.P.298 DATE: 4 December 1991 PRODUCT: NetWare PRODUCT REVISION: v3.11 SUPERSEDES: N/A SYMPTOM: Errors, such as "Unexpected code encountered in area to be patched" during implementation of patches and fixes. ISSUE/PROBLEM Because of the unanticipated success of NetWare v3.11, the available serialization range was exhausted. As a result, the v3.11 operating system has been modified to extend that serialization range. This modification has required a corresponding change to all v3.11 operating system patches, including those previously released. It does not affect any patches or fixes other than v3.11 operating system patches. When a user attempts to apply an unmodified NetWare v3.11 operating system patch to a v3.11 operating system with the extended serialization range, he or she may receive an error similar to the one above. SOLUTION The modified NetWare v3.11 operating system patches can be applied to any v3.11 operating system if the PATCHMAN.NLM (v2.20 or later) that accompanies them is loaded at the file server. PATCHMAN.NLM performs the application of a given patch to the v3.11 operating system as it resides in file server memory. Users should be aware of six important points: 1) PATCHMAN.NLM v2.20 (or later) must be loaded. 2) The modified patches, with PATCHMAN.NLM v2.20 (or later), will successfully load on NetWare v3.11 operating systems without the extended serialization range. 3) The re-released patches will not be successfully implemented if PATCHMAN NLM v2.20 (or later) is not loaded. 4) Unmodified v3.11 operating system patches will work successfully only on operating systems without the extended serialization range. They will not work on a newly modified operating system, nor on an operating system also running modified patches or PATCHMAN v2.20 (or later). 5) The re-released NetWare v3.11 operating system patches are dated October 1991 or later. 6) All NetWare v3.11 patches, with the latest PATCHMAN.NLM, are zipped into the file 311PTx.ZIP (where x was 1 at the time this bulletin was released) and this file will be updated with a successively higher value of x as v3.11 patches and PATCHMAN.NLM are updated. This file is available on NetWire in NOVLIB library 4. ***************************************************************** DISCLAIMER Novell, Inc. makes no representations or warranties with respect to any NetWare software, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of any NetWare software is forbidden without the express written consent of Novell, Inc. Further, Novell reserves the right to discontinue distribution of any NetWare software. Novell is not responsible for lost profits or revenue, loss of use of the software, loss of data, costs of re-creating lost data, the cost of any substitute equipment or program, or claims by any party other than you. Novell strongly recommends a backup be made before any software is installed. Technical support for this software may be provided at the discretion of Novell. *****************************************************************